Skip to content

SO-121: Resync Libray for 4.16 - #540

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:masterfrom
fbm3307:libresync416
Apr 11, 2024
Merged

SO-121: Resync Libray for 4.16#540
openshift-merge-bot[bot] merged 1 commit into
openshift:masterfrom
fbm3307:libresync416

Conversation

@fbm3307

@fbm3307 fbm3307 commented Apr 11, 2024

Copy link
Copy Markdown
Contributor

This for the syncing the assets folder /library for OCP 4.16 release

Signed-off-by: Feny Mehta <fbm3307@gmail.com>
@openshift-bot openshift-bot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 11, 2024
@openshift-bot

openshift-bot commented Apr 11, 2024

Copy link
Copy Markdown
Contributor

@fbm3307: This pull request references SO-121 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set.

Details

In response to this:

This for the syncing the assets folder /library for OCP 4.16 release

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@fbm3307

fbm3307 commented Apr 11, 2024

Copy link
Copy Markdown
Contributor Author

/label px-approved
/label qe-approved
/label docs-approved

@openshift-ci openshift-ci Bot added px-approved Signifies that Product Support has signed off on this PR qe-approved Signifies that QE has signed off on this PR docs-approved Signifies that Docs has signed off on this PR labels Apr 11, 2024
@openshift-bot

openshift-bot commented Apr 11, 2024

Copy link
Copy Markdown
Contributor

@fbm3307: This pull request references SO-121 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set.

Details

In response to this:

This for the syncing the assets folder /library for OCP 4.16 release

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 11, 2024
@fbm3307

fbm3307 commented Apr 11, 2024

Copy link
Copy Markdown
Contributor Author

/test e2e-aws-operator

@fbm3307

fbm3307 commented Apr 11, 2024

Copy link
Copy Markdown
Contributor Author

/override ci/prow/e2e-aws-ovn-image-ecosystem

@openshift-ci

openshift-ci Bot commented Apr 11, 2024

Copy link
Copy Markdown
Contributor

@fbm3307: Overrode contexts on behalf of fbm3307: ci/prow/e2e-aws-ovn-image-ecosystem

Details

In response to this:

/override ci/prow/e2e-aws-ovn-image-ecosystem

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci

openshift-ci Bot commented Apr 11, 2024

Copy link
Copy Markdown
Contributor

@fbm3307: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/okd-e2e-aws-ovn-upgrade c4affbd link false /test okd-e2e-aws-ovn-upgrade
ci/prow/okd-e2e-aws-ovn-image-ecosystem c4affbd link false /test okd-e2e-aws-ovn-image-ecosystem
ci/prow/okd-e2e-aws-ovn-builds c4affbd link false /test okd-e2e-aws-ovn-builds
ci/prow/okd-e2e-aws-ovn c4affbd link false /test okd-e2e-aws-ovn
ci/prow/okd-scos-e2e-aws-ovn-builds c4affbd link false /test okd-scos-e2e-aws-ovn-builds
ci/prow/okd-scos-e2e-aws-ovn-image-ecosystem c4affbd link false /test okd-scos-e2e-aws-ovn-image-ecosystem
ci/prow/okd-scos-e2e-aws-ovn-upgrade c4affbd link false /test okd-scos-e2e-aws-ovn-upgrade
ci/prow/okd-scos-e2e-aws-ovn c4affbd link false /test okd-scos-e2e-aws-ovn
ci/prow/okd-scos-e2e-aws-ovn-jenkins c4affbd link false /test okd-scos-e2e-aws-ovn-jenkins
ci/prow/okd-e2e-aws-ovn-jenkins c4affbd link false /test okd-e2e-aws-ovn-jenkins
ci/prow/okd-scos-e2e-aws-operator c4affbd link false /test okd-scos-e2e-aws-operator

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@dperaza4dustbit dperaza4dustbit left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Apr 11, 2024
@openshift-ci

openshift-ci Bot commented Apr 11, 2024

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dperaza4dustbit, fbm3307

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:
  • OWNERS [dperaza4dustbit,fbm3307]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot
openshift-merge-bot Bot merged commit 30625a6 into openshift:master Apr 11, 2024
@openshift-bot

Copy link
Copy Markdown
Contributor

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-cluster-samples-operator-container-v4.16.0-202404120544.p0.g30625a6.assembly.stream.el9 for distgit ose-cluster-samples-operator.
All builds following this will include this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. docs-approved Signifies that Docs has signed off on this PR jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. px-approved Signifies that Product Support has signed off on this PR qe-approved Signifies that QE has signed off on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants